Supporting random access of compressed data

ABSTRACT

A processing device comprising compression circuitry to: determine a compression configuration to compress source data; generate a checksum of the source data in an uncompressed state; compress the source data into at least one block based on the compression configuration, wherein the at least one block comprises: a plurality of sub-blocks, wherein the plurality of sub-block includes a predetermined size; a block header corresponding to the plurality of sub-blocks; and decompression circuitry coupled to the compression circuitry, wherein the decompression circuitry to: while not outputting a decompressed data stream of the source data: generate index information corresponding to the plurality of sub-blocks; in response to generating the index information, generate a checksum of the compressed source data associated with the plurality of sub-blocks; and determine whether the checksum of the source data in the uncompressed format matches the checksum of the compressed source data.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application is a continuation application claimingpriority from U.S. patent application Ser. No. 16/013,710, filed Jun.20, 2018, and titled “Supporting Random Access of Compressed Data”,which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to hardware processors,and more specifically, but without limitation, to supporting randomaccess of compressed data.

BACKGROUND

For “big data” applications, such as within a data center or cloudcomputing environment, large amounts of data need to be stored reliablyand in a cost-effective manner. Compression processes are generallyemployed to reduce the size of data without sacrificing the informationcontained within the data. Data consumers are required to decompress thecompressed files before using the data. Conventional compression formatsfor big data stores typically produce relatively poor compressionratios, for example, because they are fairly simplistic in an attempt toprovide efficient software implementations, while also allowing for somedegree of random access. Compression schemes such as Deflate offerbetter compression ratios, but current implementations do not allow forrandom access to compressed data. For example, column-oriented databasesare often used in big data environments to provide the desired output.However, compressed column-oriented data requires decompression of acolumn of data from a start point to a point of interest to access thepoint of interest. Thus, random accesses on compressed big data storesusing conventional techniques are generally cost and resourceprohibitive. Moreover, the compressed data, in some instances, may becorrupted during the compressing processes. Accordingly, it is desirableto confirm that the compressed data is not corrupted before beingcommitted.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure. The drawings, however, should not betaken to limit the disclosure to the specific embodiments, but are forexplanation and understanding only.

FIG. 1 illustrates a block diagram of a processing device coupled to adatabase according to various embodiments.

FIG. 2 illustrates a block diagram of a processing device includingcompression circuitry and decompression circuitry according to variousembodiments.

FIG. 3 illustrates a block diagram of a compressed source data accordingto various embodiments.

FIG. 4 illustrates a flow diagram for supporting random access ofcompressed data according to various embodiments.

FIG. 5A is a block diagram illustrating a micro-architecture for aprocessor according to an embodiment of the disclosure.

FIG. 5B is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipeline accordingto an embodiment of the disclosure.

FIG. 6 is a block diagram illustrating a micro-architecture for aprocessor in accordance with one embodiment of the disclosure.

FIG. 7 is a block diagram illustrating a system in which an embodimentof the disclosure may be used.

FIG. 8 is a block diagram illustrating a system in which an embodimentof the disclosure may operate.

FIG. 9 is a block diagram illustrating a system in which an embodimentof the disclosure may operate.

FIG. 10 is a block diagram illustrating a System-on-a-Chip (SoC)according to an embodiment of the disclosure;

FIG. 11 is a block diagram illustrating a SoC design according to anembodiment of the disclosure; and

FIG. 12 illustrates a block diagram illustrating a computer systemaccording to an embodiment of the disclosure.

DETAILED DESCRIPTION

The embodiments described herein are directed to data compressiontechniques that are capable of providing high compression ratios forcompression schemes such as Deflate while also providing random accessto compressed data. Additionally, the embodiments described hereinpermit the compressed data to be verified during compression to makesure it matches the uncompressed source data. For example, theverification, described herein, is provided by checksums which can workin various ways. During compression, the final checksum gives areasonable assurance that the compressed data can be successfullydecompressed (i.e. that the compression was not corrupted). Duringdecompression, the checksum gives a reasonable assurance that the bitstream didn't get corrupted after compression and that the indexing intothe compressed stream was correct (i.e. that the data wasn't corruptedin storage, and that the decompress process was performed properly).

Various embodiments may be generally directed to techniques for datacompression provided by a computer system. The computer system mayinclude compression circuitry operative to perform a compression processto compress source data to generate compressed data. In someembodiments, the source data may include data from one or more “bigdata” sources. A non-limiting example of a big data source may include acolumn-oriented database, for instance, from a column-oriented databasemanagement system (DBMS). In some embodiments, the compression processmay generate compressed data formed of discrete blocks comprising one ormore sub-blocks (or “mini-blocks”). In various embodiments, eachsub-block may only include information (for instance, “history”information) that references data within that sub-block. Accordingly,each sub-block may not include history information from other discretesub-blocks of the compressed data. In various embodiments, each discretesub-block may be decompressed without requiring decompression of otherdata elements, for instance, such as other discrete sub-blocks. Invarious embodiments, the compression process may generate a block indexthat includes data for individually accessing the discrete sub-blocks.The block index may also include a checksum associated with the datarelated to the sub-blocks.

Additionally, in some embodiments a decompress-verify process isprovided to prevent data loss. A decompress-verify process decompressescompressed data and checks (via a checksum) against the original databefore the compressed data can be committed. This ensures no soft-errors(or obscure bugs) in the compression process corrupted the data suchthat it cannot be decompressed later from storage.

In general, random operations may include any type of operation onspecified data of interest (“operation target”), or a portion of thecompressed data that includes specified data of interest. For example, auser desires to access uncompressed data at a particular byte (e.g.,byte x). In some embodiments, a random operation may include a randomaccess to the compressed data. For example, the compressed data mayinclude a compressed bit stream having discrete sub-blocks b0-b100 andthe operation target may be located within b50. In a conventionalsystem, a decompression process to locate and decompress data ofinterest would be required, among other things, to decompress the datafrom a starting data block (for instance, a first Deflate block) to thedata block containing the operation target (for instance, a secondDeflate block), or to decompress an entire Deflate block in order toaccess only a portion of the Deflate block. However, a decompressionprocess according to some embodiments may operate to locate anddecompress only discrete sub-block b50 (which may be one of a pluralityof discrete sub-blocks making up a Deflate block) in order to access theoperation target. In this manner, compression processes according tosome embodiments are able to provide compressed data having highcompression ratios.

Various embodiments may be generally directed to techniques for datacompression and a decompress-verify process provided by a computersystem. In one embodiment, a processing device of a computer systemcomprising compression circuitry to: determine a compressionconfiguration to compress source data; generate a checksum of the sourcedata in an uncompressed state; compress the source data into at leastone block based on the compression configuration, wherein the at leastone block comprises: a plurality of sub-blocks, wherein the plurality ofsub-block includes a predetermined size; a block header corresponding tothe plurality of sub-blocks; and decompression circuitry coupled to thecompression circuitry, wherein the decompression circuitry to: while notoutputting a decompressed data stream of the source data: generate indexinformation corresponding to the plurality of sub-blocks; in response togenerating the index information, generate a checksum of the compressedsource data associated with the plurality of sub-blocks; and determinewhether the checksum of the source data in the uncompressed formatmatches the checksum of the compressed source data.

FIG. 1 depicts an operating system that may be representative of variousembodiments. The operating system may include processing device 100.Processing device 100 may include, among other things, memory 101, core102, compression circuitry 110 and decompression circuitry 120 that arecoupled to one another. Processing device 100 may include one or morecores.

As shown in FIG. 1, processing device 100 may include compressioncircuitry 110. In various embodiments, compression circuitry 110 mayinclude or may be disposed within a processor circuit, a SoC, afield-programmable gate array (FPGA), and/or the like. In

some embodiments, compression circuitry 110 may include a processorcircuit.

In some embodiments, compression circuitry 110 may be implemented insoftware, firmware, hardware, or a combination thereof. In variousembodiments, compression circuitry 110 may be implemented in hardwareconfigured to execute software, firmware, and/or the like to performoperations according to some embodiments. In some embodiments,compression circuitry 110 may be or may include a compression softwareapplication operative to compress data to generate compressed dataaccording to some embodiments. In some embodiments, compressioncircuitry 110 may be or may include a compression software applicationexecuted by a processor circuit. Compression circuitry 110 may include adata input/output interface (not shown) configured to access source data130. Compression circuitry 110 then compresses the source data togenerate compressed data 138 (e.g., blocks and sub-blocks). An exampleof compressed data is depicted in FIG. 3 which will be described infurther detail below.

In various embodiments, compressed data 138 may include compressed dataformed of discrete blocks (e.g., a Deflate block or Deflate-basedblock). The blocks of compressed data may be formed of various blockelements, including, without limitation, headers and sub-blocks.

In some embodiments, source data 130 may include uncompressed data. Invarious embodiments, source data 130 may include compressed datagenerated using conventional compression techniques (for instance,compressed data that does not include discrete sub-blocks or mini-blocksaccording to some embodiments). Accordingly, in some embodiments,compression circuitry 110 (for instance, in combination withdecompression circuitry) may operate to transform conventionalcompressed data into compressed data 138 (that includes blocks andsub-blocks).

Compression circuitry 110 may receive source data 130 from varioussources, including software applications or threads, hardware elements,data buffers, and/or the like. For instance, source data 130 may beobtained from database 150. In various embodiments, database 150 mayinclude data from a big data platform, such as a data center, cloudcomputing environment, distributed computing environment, socialnetworking platform, business analytics platform, and/or the like. Ingeneral, a big data platform may be defined by various characteristicsof the data associated with the platform, such as the volume, velocity,variety, and/or value of the data. In some embodiments, database 150 mayinclude a column-oriented (or columnar) database, for instance, of aDBMS. In general, a column-oriented database stores data by columnsinstead of by row. In a column-oriented database, each column may bestored separately, with attribute values of the same column storedcontiguously. Although column-oriented databases are used in someexamples, embodiments are not so limited as other types of databases maybe used as database 150 or as source data 130 according to someembodiments. Non-limiting types of other databases may includerelational databases, correlation databases, object databases,hierarchical databases, and/or the like.

In addition, database 150 and source data 130 may include databases ordata sources from various proprietary and/or open source platforms, suchas Oracle®, Microsoft® SQL Server, IBM® Informix®, SAP® Sybase®, and/orthe like. In various embodiments, source data 130 may be in the form ofa data sequence or stream received by or otherwise accessed bycompression circuitry 110. A data buffer (not shown) may be used tostore data, such as intermediate data, data waiting to be compressed,compressed data waiting to be transmitted, and/or the like. In someembodiments, compression circuitry 110 may access compressed data storedwithin the data buffer for transmission to a consumer of the compresseddata.

Compression circuitry 110 is operative to compress source data 130 togenerate compressed data 138. In various embodiments, compressioncircuitry 110 accesses or generates a checksum (e.g., cyclic redundancycheck (CRC)) of the source data 130. The checksum of the uncompressedsource data 130 is then compared with a calculated checksum (e.g., CRC)of the uncompressed data that is output from the decompressor (orcompare the checksum of the uncompressed data that is output from thedecompressor against a stored checksum of the uncompressed data) toverify, among other things, that the compressed data is not corrupted,which will be described in further detail below. Additionally,compression circuitry 110 compresses source data based on compressionconfiguration, which will also be described in further detail below.

In various embodiments, compression circuitry 110 may include acompression engine, algorithm, process, software application, firmwareapplication, processor, co-processor, FPGA, and/or the like. Compressioncircuitry 110 may be configured to encode or compress data using adiscrete compression process according to some embodiments. The discretecompression process may be based on one or more existing compressionprocesses. Non-limiting examples of compression processes may includelossless data compression, Lempel-Ziv (LZ), LZ77, LZ4, LZFX, LZSS,Deflate, Snappy, Huffman encoding, compressed adaptive index (COMPAX),improved COMPAX (ICX), single-pass recompression (SPR), and/or the like.

In some embodiments, the discrete compression process performed bycompression circuitry 110 may include a variation of LZ77 compressionand/or Deflate. For example, the discrete compression process mayoperate using a Deflate compression process except that, among otherthings, instead of generating compressed data formed of conventionalDeflate blocks, the discrete compression process may generate discretecompressed data that includes discrete sub-blocks according to someembodiments. In various embodiments, the discrete compressed data mayinclude Deflate blocks formed of one or more discrete sub-blocks. Ingeneral, and as described in more detail below, a conventional Deflatecompression process may keep track of history information in eachDeflate block. Accordingly, at any point in the Deflate-compressed data,such as for a particular Deflate block, there is history information ofthe preceding characters for a certain window (which may include data inone or more other Deflate blocks), such as 32 KB. A 32 KB sliding windowmeans that the compressor (and decompressor) have a record of what thelast 32768 (32*1024) characters were. Accordingly, decompressing data ofan operation target stored in a Deflate block, requires decompressing atleast an entire Deflate block as well as any blocks referred to in thehistorical information of the Deflate block (which may also includehistorical information referring to still other Deflate blocks, and soon). However, in some embodiments, the discrete compression process mayuse a LZ77-based and/or Deflate-based compression process, but maygenerate compressed data formed of, among other things, discrete blocksaccording to some embodiments instead of conventional Deflate blocks.For instance, in some embodiments, the discrete sub-blocks may notinclude historical information that references other discrete sub-blocks(the historical information may point to other data within the samediscrete sub-block). In some embodiments, each discrete sub-block mayinclude all of the information necessary to decompress the discretesub-block and does not rely on other discrete sub-blocks in order to bedecompressed. Although LZ77 and Deflate are used as examples,embodiments are not so limited as any compression process capable ofbeing used according to some embodiments is contemplated herein.

In general, the LZ77 compression process operates by replacing repeatedoccurrences of data with references to previous occurrences of that dataexisting earlier in the input (uncompressed) data stream. A match isencoded by a pair of numbers called a length-distance pair (“distance”may be referred to as an “offset”). As such, the LZ77 compressionprocess finds repeated substrings and replaces them with backwardreferences (relative distance offsets). The LZ77 compression process canuse a reference to a duplicated string if the relative distance is lessthan the maximal history size defined in the algorithm encoding (forinstance, 32 KB in Deflate). The compressed data consists of a series ofelements of two types: literal bytes (copy of the data) and pointers toreplicated strings, where a pointer is represented as the pair <length,backward distance>. The various algorithms in the LZ77 family all findLZ77 string matches during compression, but encode the literals orreferences differently (for instance, Huffman codes in Deflate, simplebyte-oriented packing in Snappy, and/or the like), and have differentmaximal history windows. In general, a literal may include raw encodeddata (as opposed to data encoded as a length, distance pair).

To spot matches, the LZ77 encoder keeps track of some amount of the mostrecent data, such as the last 2 kB, 4 kB, 32 kB, and/or the like. Thestructure in which this data is held is called a “sliding window” or“history window” (accordingly, LZ77 is sometimes referred to as slidingwindow compression). The encoder keeps the most recent data within thesliding window to look for matches (and the decoder likewise will keepthis data to interpret the matches the encoder refers to). Accordingly,at any point in the data, such as for a particular Deflate block, thereis a record (“history” or “history information”) of the precedingcharacters (which may be in one or more other Deflate blocks). A 32 KBsliding window means that the compressor (and decompressor) have arecord of what the last 32768 (32*1024) characters were.

During LZ77 compression, byte patterns of a preceding (earlier or older)portion of a byte stream may be compared against a current portion (orcurrent bit sequence) of the byte stream. If a sequence of bytes isfound in the current portion that matches a sequence of bytes in thepreceding portion (or preceding byte sequence), the sequence of bytes inthe current portion is replaced with a reference to the same sequence ofbytes in the earlier portion.

The reference that is inserted for the current byte sequence identifiesthe length of the current byte sequence and the location of thepreceding byte sequence expressed, for instance, as a “distance” fromthe current byte sequence to the matching preceding byte sequence. Assuch, the LZ77 compression process encodes a byte sequence as a “length,distance pair” that is inserted in the byte stream in place of a currentbyte sequence. Upon decoding the compressed stream, when the decoderreaches the length, distance pair that is embedded in the byte stream,the decoder uses the distance part of the length, distance pair to referback to the start of the matching byte sequence and reproduces thecorrect byte sequence of the decoded stream by reproducing a number ofbytes from the start of the matching byte sequence that is equal to thelength component of the length, distance pair.

A non-limiting example of an LZ77 compression process may be performedon the following illustrative sequence, recited in a form prior tocompression: “ABCD BBBB BC CDE DEFG BBBB EFGH.” During compression, theLZ77 compression process may locate the match “BBBB,” having a length of6 (including spaces). The matching “BBBB” sequences have a match offset(for instance, an intervening distance) of 15. The compressed sentencemay be in the following form: “ABCD BBBB BC CDE DEFG @(6,15) EFGH,” with“(6,15)” being the length and distance pair associated with the BBBBmatch.

The Deflate compression process is used as the bases of variouscompression platforms, such as gzip/Zlib and Winzip/PKzip. In general,Deflate uses a series of blocks (Deflate blocks) corresponding tosuccessive blocks of input data. Each block may be compressed using acombination of the LZ77 compression process and Huffman coding. Asdescribed above, the LZ77 compression process operates to find repeatedsubstrings and replaces the repeated substrings with references, such asrelative distance offsets. The LZ77 compression process may use areference to a duplicated string occurring in the same block or previousblocks, for instance, up to 32 KB previous input bytes (a “history” or“history information”). The compressed data may include a series ofelements of two types: literal bytes and pointers to replicated strings(represented as the pair: <length, backward distance>. The LZ77compression process operates to find string matches at each position

Using data structures to efficiently index locations where matchingstrings may be found, the LZ77 compression process may operate to searcha number of locations to determine a “best” match. The effort (forinstance, the number of searches attempted) is specified by thecompression level. For instance, gzip/Zlib defines a number ofcompression levels, ranging from 1 to 9, with 9 being the highestcompression level and requiring the highest processing cost. A file maybe represented as a series of tokens, where each token may represent aliteral byte or a match of text that occurred previously. The tokens maybe encoded using a variable-size code (for instance, a Huffman codefollowed by certain “extra bits”).

As shown in FIG. 1, processing device 100 may include decompressioncircuitry 120. Decompression circuitry 120 is operable to decompresscompressed data, such as discrete compressed data 138 to generatedecompressed data 132. In some embodiments, decompression circuitry 120may operate to generate index information 134 during thedecompress-verify process (subsequent to or concurrently with thecompression process). In some embodiments, index information 134 mayinclude information for decompression circuitry to access data withindiscrete compressed data 138, such as data at a particular block (forinstance, a Deflate block) and/or discrete sub-block of discretecompressed data 138. For example, index information 134 may include anindex array or other data structure that may record offset informationfor Deflate blocks and/or sub-blocks of discrete compressed data 138. Invarious embodiments, the offset information may include a starting bitoffset for each discrete block, a bit offset for a first token of eachdiscrete block, a bit offset of headers associated with the discreteblocks, and/or the like. In some embodiments, decompression circuitry120 may use index information 134 to decompress discrete compressed data138 to generate decompressed data 132.

In various embodiments, index information 134 is provided to index table140. Index table 140, in various embodiments, is generated bydecompression circuitry 120. In one embodiment, decompression circuitry120 include index table 140. Alternatively, decompression circuitry 120does not include index table 140. For example, index table 140 is storedin memory.

It should be appreciated that it may be advantageous to perform some ofthe operations during decompression because the meta-data doesn't haveto be stored for cold compressed data. When the data gets accessed fromcold-storage, one can perform a sequential decompress. Additionally, there-generated meta-data is available as long as the column is hot/warm,enabling further random-access reads to be efficient.

Decompression circuitry 120, in various embodiments, generates checksumdata 136 in response to decompression circuitry 120 generating indexinformation 134. As will be described in further detail below, checksumdata 136 is a cumulative checksum corresponding to sub-blocks in thecompressed data. Checksum data 136 is also provided to index table 140.Accordingly, index table 140 includes index information 134 as well aschecksum data 136 corresponding to particular components of compresseddata 138 (e.g., header, block, sub-block, etc.).

Decompression circuitry 120, in various embodiments, determines whetherthe checksum of the uncompressed source data (accessed/generated bycompression circuitry 110) matches the checksum data 136 of thecompressed data, and whether compression circuitry 110 generated themini-blocks appropriately, which will be described in further detailbelow.

In various embodiments, compression circuitry 110 includes one outputfor outputting compressed data 138. As a result, compression circuitry110, in various embodiments, is unable to concurrently generate andoutput index information 134 and/or checksum data 136. Accordingly,decompression circuitry 120 is able to (while not outputtingdecompressed data 132) generate index information 134 and/or checksumdata 136 while compression circuitry 110 is generating compressed data138. Alternatively, in some embodiments, the processing related to theindex information is provided by the compression circuitry (during theverify flow). For example, the compression circuitry can buffer alimited number of some sizes of sub-blocks (e.g., 128) and then writeout an output stream, or to a configuration space where state is saved.

In various embodiments, discrete compressed data 138 may include aDeflate (or Deflate-based) compression stream such that discretecompressed data 138 may be decompressed using a Deflate-compliantcompressor. In various embodiments, to perform a random operation ondiscrete compressed data 138, such as decompressing discrete compresseddata 132, decompression circuitry 120 may use index information 134 todetermine which discrete block includes an operation target and where acorresponding header (for instance, Deflate header of a correspondingDeflate block) is located (see, for example, FIG. 3). The header wouldthen be conceptually appended to the discrete sub-block and the discretesub-block would be decompressed. This is done to gain the effect ofdecompressing the combined data without needing to actually append thedata. In one embodiment, for example, if the decompressor supportedappropriate gather functionality, then the header and the sub-blockcould be specified as entries on the gather list. Accordingly, todecompress a single element according to some embodiments, a discretedecompression process would only have to decompress, on average, half ofa discrete block (compared with an entire column of data for compressedcolumn-orientated data).

FIG. 2 illustrates an example of an operating environment that may berepresentative of various embodiments. The operating environmentdepicted in FIG. 2 may include processing device 100 including, amongother things, compression circuitry 110 and decompression circuitry 120.Compression circuitry 110 may be operative to generate discretecompressed data 138. In some embodiments, compression circuitry 110 maybe implemented in hardware and/or software executed via processorcircuit. In various embodiments, compression circuitry 110 may beconfigured to operate a LZ77-based and/or Deflate-based discretecompression process. In general, compression circuitry 110 may beconfigured to operate a discrete compression process according to someembodiments to compress data according to a Deflate-based compressionprocess using discrete blocks in place of or in combination withconventional Deflate blocks.

As shown in FIG. 2, an LZ77 search engine 240 of compression circuitry110 may receive source data 130. LZ77 search engine 240 may analyzesource data 130 for repeated patterns. Repeated patterns of a certainlength (for instance, greater than or equal to 3 characters) may bereduced to a length-distance pair token. The tokens 242 may be providedto an encoder 244, such as a Huffman encoder. Encoder 244 may operate toencode tokens 242, for instance, by encoding most-frequently seen tokens242 with a minimum size bit symbol.

In various embodiments, encoder 244 may generate blocks 250-1 to 250-n.In some embodiments, blocks 250 may be Deflate blocks formed of discretesub-blocks. In various embodiments, encoder may generate blocks 250 thatinclude a predetermined number of discrete sub-blocks. For example,encoder 244 may generate a new Deflate block every n sub-blocks, where nmay include 1, 2, 3, 4 and so on. Accordingly, in some embodiments, eachDeflate block includes a certain number of integral, undivided discreteblocks (for instance, a sub-block may not span multiple Deflate blocks).

A discrete sub-block may be configured to include a certain amount ofdata. In some embodiments, the predetermined amount of data may include1 kb, 2 kb, 3 kb, etc. It should be appreciated that the sub-block caninclude any predetermined amount of data. In some embodiments, eachsub-block includes a predetermined amount of data (e.g., each sub-blockincludes 1 kb of data). In some embodiments, discrete blocks may havedifferent amounts data. In some embodiments, discrete blocks may eachhave the same (or substantially similar) amount or limit on the amountof data. In various embodiments, each discrete block may include a fixedamount of about 1 KB of uncompressed data. In some embodiments, theamount of data may not be constrained from the Deflate standard and asub-block may be generated after a first token 242 that reaches the nextsub-block boundary.

A discrete compression process according to some embodiments maygenerate various compression configurations based on one or morecharacteristics, such as block size, sub-block size, number ofsub-blocks in each Deflate block, and/or the like.

For example, a compression configuration including sub-block of size 1KB with four discrete sub-blocks per Deflate block may have acompression configuration of ¼. In another example, a compressionconfiguration may include 1/16 with a sub-block size of 1 KB and blocksize of 16 KB (for instance, 16 discrete blocks per high-level block).

In some embodiments, compression circuitry 110 truncates a last match sothat the length does not cross into the next sub-block, by possiblyencoding last few bytes as literals. As described above, the compressioncircuitry provided a predetermined sub-block size (e.g., 1 kb). However,the compression circuitry may generate a sub-block that is slightlylarger than the predetermined sub-block size in order to save a lastmatch that may extend beyond the sub-block having a predetermined size.If a sub-block is generated with a size that beyond the predeterminedsub-block size, then the index table would include additionalinformation to properly decompress the sub-blocks. For example, in oneembodiment, the index table would further include the boundaries of asub-block in both the compressed data stream and in uncompressed datastream.

In various embodiments, compression circuitry 110 may use one or moredefault compression configurations to generate discrete compressed data.In some embodiments, compression circuitry 110 may use an optimalcompression configuration determined to provide one or more optimalcompression characteristics (for instance, compression ratio,compression speed, and/or the like) for the data being compressed. Insome embodiments, optimal compression configurations for a particulardata source (for instance, a column-oriented database) may be stored,such as in memory or as meta data in a database associated with a datasource, and may be looked up by compression circuitry 110 for use duringa discrete compression process.

Decompression circuitry 120 is coupled to compression circuitry 110 andis operable to generate decompressed data 132, offsets 260 and checksums262, which will be described in further detail below. Decompressioncircuitry 120, in various embodiments, is provided two flags (notcurrently in the Deflate scheme) as indicated in Table 1 below:

TABLE 1 Disable_Decompress_Output 1-bit Doesn't write decompressed bytesto output stream Index_Size 3-bit Defines sub-blocks (512 . . . 32k,etc.), zero disable features

If the bits (with respect to Table 1) are both 0, then decompressionoccurs as a normal operation generating the uncompressed stream.

If disable_decompress_output is set, and index-size is 0, thendecompression occurs as a normal operation. The checksum (e.g., CRC) iscalculated but no decompressed output is written to the output stream.This is to aid some decompress-verify flows on checksum data.

If index_size is non-zero, then disable_decompress_output must be set.The following concerns the case where index_size is non-zero (i.e. wherea sub-block scheme has been used while compressing). The index_sizedefines the sub-block size. The sub-block size is a power of 2 (>=512).In this mode, the expectation is that the act of decompressing is toverify the compressed bit-stream in entirety, as well as the formationof mini-blocks, via CRCs (and not really output the uncompressed data).The uncompressed data is written out from output accumulators in thedecompression circuitry but suppressed from the write-port. Thewrite-port is reserved instead for writing out the stream of bit-indexand CRC meta-data per sub-block.

The decompression circuitry checks for the following to ensure validconstruction of blocks/sub-blocks by the compression circuitry:

-   -   1. If a Deflate Block header is seen, and the cumulative number        of output bytes is not a multiple of the mini-block size, then        decompression circuitry returns an error. The exception to this        are zero-length stored blocks.    -   2. If the output of a match token (reference, len-dist)        straddles two mini-blocks, the decompression circuitry returns        an error.    -   3. If a stored block is seen, and the size is not a multiple of        the mini-block size, the decompression circuitry returns an        error. This check can be done just for non-final blocks. This        check should be done for blocks other than zero-length stored        blocks.    -   4. If the output overflows, it is a non-recoverable error.    -   5. The normal distance check error that will be modified when        there is a sub-block specified. After every sub-block, it is        ensured that the valid-distance drops to 0 and then starts to        count up again. Thus, a more stringent distance check is        performed for the references when a sub-block has been        specified. This guarantees that the overall deflate stream will        also be well-formed.

It should be appreciated that above list of checks is non-limiting list.In various embodiments, more or less checks may be performed.

A general write flow is described below, according to some embodiments.

First, the compressor is configured with sub block size and sub-blockmode.

Second, the source data is compressed and the CRC for the wholeuncompressed data is determined.

Third, the decompressor is configured decompress-verify mode using CRCsbut also with sub-block mode enabled.

Fourth, the decompressor does not output the uncompressed data butcomputes the CRC of the whole data stream and periodically outputtingthe cumulative CRC (e.g., checksums 262) up to a given point (e.g.,offsets 260). For example, given the cumulative CRC at the start of asub-block and the cumulative CRC at the end of the sub-block (and thesize of the sub-block), one can compute the CRC of the sub-block, butneither cumulative CRC is the CRC of that sub-block (except for the caseof the first sub-block, where the initial CRC is 0). Specifically, ifthe sub-block size was 100 bytes, the CRCs of the following regions arecomputed: (0 . . . 99), (0 . . . 199), (0 . . . 299), etc.

Fifth, the decompressor verifies if every sub-block was correctlygenerated in the deflate stream and checks the whole-file checksum fromthe decompressor against the one computed by the compressor.

A general read flow is described below, according to some embodiments.

If a whole column/file is needed, the decompressor is set up to read anormal deflate stream as usual.

If a random access is needed, and no meta-data is available (e.g.,indices and the CRC data), the decompressor generates sub-blockmeta-data (the sub-block size used by the compressor has to be known ata minimum, but this can be a parameter for the whole database, ortable).

For random access with meta-data available (e.g., indices and the CRCdata), the starting sub-block position is determined and thedecompressor is loaded with bit-stream containing the deflate header(e.g., parsing the Huffman tables and saving state). Then, a second jobis submitted with the actual start of sub-block symbols after restoringthe saved state.

FIG. 3 depicts an illustrative compressed data stream according to someembodiments. As shown in FIG. 3, a compressed data stream 300 mayinclude various elements, including blocks 310, headers 320 andsub-blocks 330. In some embodiments, data stream 300 may include Deflateblocks 310, which may be formed of headers 320 and/or sub-blocks 330. Itshould be appreciated that sub-blocks 30 represent Huffman encoded data,and blocks 310-2 and 310-4 are zero-length stored blocks that do nothave any data following them.

In various embodiments, a decompression circuitry 120 may generate indexinformation 134 (e.g., offsets 340) that may include element informationassociated with elements of discrete compressed data stream, such asDeflate blocks 310, headers 320, and sub-blocks 330.

In some embodiments, index information 134 may include an index array(e.g., index table 140) configured to include element information suchas offsets 340. Non-limiting examples of offsets may include thestarting bit offset of each discrete block, as the discrete blocks arenot byte-aligned. In various embodiments, the arrow references of indexinformation 134 (e.g., offsets 340) depicted in FIG. 3 may represententries into the index array.

In various embodiments, the output of the offsets 340 is generated inthe following circumstances/rules:

-   -   1. When the number of bytes “written” out of the output        accumulator is a multiple of the sub-block size, then the input        bit offset of the following token is written to the output        stream.    -   2. At the end of decompression, if any bytes were “written”        since the last output, then the bit offset of the end of the        input stream is written.    -   3. When a deflate header is finished being parsed, and it is not        a zero-length stored block, the bit offset of the next token is        written.

Additionally, in some embodiments, when a bit offset is written, the CRCof all of the input data up to that point is also written. As a result,8 bytes are written at a time.

Table 2 below, is an example index table 140 that includes the offsetand corresponding checksum (e.g., CRC) with respect to compressed datastream 300.

TABLE 2 Offset CRC Offset 340-1 Initial CRC (0) Offset 340-2 CRC of datafrom Offset 340-1 to Offset 340-2 Offset 340-3 CRC of data from Offset340-1 to Offset 340-3 Offset 340-4 Same as previous entry Offset 340-5CRC of data from Offset 340-1 to Offset 340-5 Offset 340-6 CRC of datafrom Offset 340-1 to Offset 340-6

Referring to Table 2, it should be appreciated that the CRC is the CRCof the uncompressed data represented by the compressed data betweenoffsets (e.g., between offset 340-1 and 340-3). In various embodiments,the index table can include bit-offsets for other items in thecompressed bit-stream that do not change the uncompressed byte-streamsuch as, but not limited to, end-of-block symbols, empty stored-blocksused for padding the compressed bit-stream, etc.

Referring to the circumstances/rules to generate the index table aboveand data stream 300, Table 2 (e.g., index table) is created as follows:

Assuming that offset 340-1 is at the start of the file, the initial CRCis 0. When the parser gets to the end of header 320-1, it will write thebit-offset 340-1 to the output using rule 3. The CRC would be 0.

When the decompressor “output” the bytes up to the end of sub-block330-1, it would write the bit-offset 340-2 using rule 1. The CRC wouldinclude the data from 340-1 to 340-2. The same thing happens at the endof sub-block 330-2.

When the decompressor finishes parsing header 320-2, it is the exceptioncase of rule 3, so nothing is written. When the decompressor finishesparsing header 320-3, by rule 3, it writes out offset 340-4. At the endof sub-block 330-3, the same thing happens as at offset 340-2.

When the decompressor gets to the end of block header 320-4, assumingthat the input file was not a multiple of the mini-block size, rule 1would not apply. At the end of header 320-4, rule 3 would not apply.Then, since this is at the end of the file, rule 2 writes offset 340-6.If the file size were a multiple of the sub-block size, then the offsetof the start of header 320-4 would be written instead, and then nofurther offsets would be written.

Referring to at least Table 2 above, in some embodiments, the checksum(e.g., CRC) of a sub-block is defined to be the checksum of all of thedata up to the end of the sub-block (e.g., inclusive of all precedingsub-blocks). This enables to generate the sub-block checksum and thefull deflate stream checksum using the same circuit (since a snapshot ofthe checksum state at additional points is needed and subsequentlyoutputted).

FIG. 4 depicts a flow diagram of method 400 for supporting random accessof compressed data, according to an embodiment.

At 410, a compression configuration to compress source data isdetermined. For example, compression circuitry 110 accesses (orgenerates) the compression configuration (e.g., sub-block size, numberof sub-blocks in a block, etc.) for compressing the source data.

At 420, a checksum of the source data in an uncompressed state isgenerated. For example, compression circuitry accesses (or generates) aCRC of the uncompressed source data,

At 430, the source data is compressed into at least one block based onthe compression configuration. For example, the block of compressed dataincludes a plurality of sub-blocks that each include a predeterminedsize (e.g., ˜1 kb) and a block header of the block.

At 440, while the decompression circuitry is not outputting adecompressed data stream of the source data, the decompression circuitrygenerates index information corresponding to the plurality ofsub-blocks. For example, an index array is generated that records thebit offset of the first token/symbol of each sub-block and the startingbit offset of the Deflate block headers.

At 450, in response to generating the index information, a checksum ofthe compressed source data associated with the plurality of sub-blocksis generated. For example, the index array also records the CRC at eachsub-block. The CRC of at each sub-block is the CRC of all data up theend of the particular sub-block (inclusive of all preceding sub-blocks).

At 460, it is determined whether the checksum of the source data in theuncompressed format matches the checksum of the compressed source data.For example, the CRC of the uncompressed source data (generated by thecompression circuitry) is compared with the CRC of the compressed sourcedata (generated by the decompression circuitry). If the CRCs are thesame then it is assumed that the source data was compressed without anyerrors/bugs. If the CRCs are not the same then it is assume that thecompression of the source data may include errors/bugs.

FIG. 5A is a block diagram illustrating a micro-architecture for aprocessor 500 that implements the processing device includingheterogeneous cores in accordance with one embodiment of the disclosure.Specifically, processor 500 depicts an in-order architecture core and aregister renaming logic, out-of-order issue/execution logic to beincluded in a processor according to at least one embodiment of thedisclosure.

Processor 500 includes a front end unit 530 coupled to an executionengine unit 550, and both are coupled to a memory unit 570. Theprocessor 500 may include a reduced instruction set computing (RISC)core, a complex instruction set computing (CISC) core, a very longinstruction word (VLIW) core, or a hybrid or alternative core type. Asyet another option, processor 500 may include a special-purpose core,such as, for example, a network or communication core, compressionengine, graphics core, or the like. In one embodiment, processor 500 maybe a multi-core processor or may be part of a multi-processor system.

The front end unit 530 includes a branch prediction unit 532 coupled toan instruction cache unit 534, which is coupled to an instructiontranslation lookaside buffer (TLB) 536, which is coupled to aninstruction fetch unit 538, which is coupled to a decode unit 540. Thedecode unit 540 (also known as a decoder) may decode instructions, andgenerate as an output one or more micro-operations, micro-code entrypoints, microinstructions, other instructions, or other control signals,which are decoded from, or which otherwise reflect, or are derived from,the original instructions. The decoder 540 may be implemented usingvarious different mechanisms. Examples of suitable mechanisms include,but are not limited to, look-up tables, hardware implementations,programmable logic arrays (PLAs), microcode read only memories (ROMs),etc. The instruction cache unit 534 is further coupled to the memoryunit 570. The decode unit 540 is coupled to a rename/allocator unit 552in the execution engine unit 550.

The execution engine unit 550 includes the rename/allocator unit 552coupled to a retirement unit 554 and a set of one or more schedulerunit(s) 556. The scheduler unit(s) 556 represents any number ofdifferent schedulers, including reservations stations (RS), centralinstruction window, etc. The scheduler unit(s) 556 is coupled to thephysical register file(s) unit(s) 558. Each of the physical registerfile(s) units 558 represents one or more physical register files,different ones of which store one or more different data types, such asscalar integer, scalar floating point, packed integer, packed floatingpoint, vector integer, vector floating point, etc., status (e.g., aninstruction pointer that is the address of the next instruction to beexecuted), etc. The physical register file(s) unit(s) 558 is overlappedby the retirement unit 554 to illustrate various ways in which registerrenaming and out-of-order execution may be implemented (e.g., using areorder buffer(s) and a retirement register file(s), using a futurefile(s), a history buffer(s), and a retirement register file(s); using aregister maps and a pool of registers; etc.).

In one implementation, processor 500 may be the same as processingdevice 100 as described with respect to FIGS. 1 and 2.

Generally, the architectural registers are visible from the outside ofthe processor or from a programmer's perspective. The registers are notlimited to any known particular type of circuit. Various different typesof registers are suitable as long as they are capable of storing andproviding data as described herein. Examples of suitable registersinclude, but are not limited to, dedicated physical registers,dynamically allocated physical registers using register renaming,combinations of dedicated and dynamically allocated physical registers,etc. The retirement unit 554 and the physical register file(s) unit(s)558 are coupled to the execution cluster(s) 560. The executioncluster(s) 560 includes a set of one or more execution units 562 and aset of one or more memory access units 564. The execution units 562 mayperform various operations (e.g., shifts, addition, subtraction,multiplication) and operate on various types of data (e.g., scalarfloating point, packed integer, packed floating point, vector integer,vector floating point).

While some embodiments may include a number of execution units dedicatedto specific functions or sets of functions, other embodiments mayinclude only one execution unit or multiple execution units that allperform all functions. The scheduler unit(s) 556, physical registerfile(s) unit(s) 558, and execution cluster(s) 560 are shown as beingpossibly plural because certain embodiments create separate pipelinesfor certain types of data/operations (e.g., a scalar integer pipeline, ascalar floating point/packed integer/packed floating point/vectorinteger/vector floating point pipeline, and/or a memory access pipelinethat each have their own scheduler unit, physical register file(s) unit,and/or execution cluster—and in the case of a separate memory accesspipeline, certain embodiments are implemented in which only theexecution cluster of this pipeline has the memory access unit(s) 564).It should also be understood that where separate pipelines are used, oneor more of these pipelines may be out-of-order issue/execution and therest in-order.

The set of memory access units 564 is coupled to the memory unit 570,which may include a data prefetcher 580, a data TLB unit 572, a datacache unit (DCU) 574, and a level 2 (L2) cache unit 576, to name a fewexamples. In some embodiments DCU 574 is also known as a first leveldata cache (L1 cache). The DCU 574 may handle multiple outstanding cachemisses and continue to service incoming stores and loads. It alsosupports maintaining cache coherency. The data TLB unit 572 is a cacheused to improve virtual address translation speed by mapping virtual andphysical address spaces. In one exemplary embodiment, the memory accessunits 564 may include a load unit, a store address unit, and a storedata unit, each of which is coupled to the data TLB unit 572 in thememory unit 570. The L2 cache unit 576 may be coupled to one or moreother levels of cache and eventually to a main memory.

In one embodiment, the data prefetcher 580 speculativelyloads/prefetches data to the DCU 574 by automatically predicting whichdata a program is about to consume. Prefeteching may refer totransferring data stored in one memory location of a memory hierarchy(e.g., lower level caches or memory) to a higher-level memory locationthat is closer (e.g., yields lower access latency) to the processorbefore the data is actually demanded by the processor. Morespecifically, prefetching may refer to the early retrieval of data fromone of the lower level caches/memory to a data cache and/or prefetchbuffer before the processor issues a demand for the specific data beingreturned.

The processor 500 may support one or more instructions sets (e.g., thex86 instruction set (with some extensions that have been added withnewer versions); the MIPS instruction set of MIPS Technologies ofSunnyvale, Calif.; the ARM instruction set (with optional additionalextensions such as NEON) of ARM Holdings of Sunnyvale, Calif.).

It should be understood that the core may support multithreading(executing two or more parallel sets of operations or threads), and maydo so in a variety of ways including time sliced multithreading,simultaneous multithreading (where a single physical core provides alogical core for each of the threads that physical core issimultaneously multithreading), or a combination thereof (e.g., timesliced fetching and decoding and simultaneous multithreading thereaftersuch as in the Intel® Hyperthreading technology).

While register renaming is described in the context of out-of-orderexecution, it should be understood that register renaming may be used inan in-order architecture. While the illustrated embodiment of theprocessor also includes a separate instruction and data cache units anda shared L2 cache unit, alternative embodiments may have a singleinternal cache for both instructions and data, such as, for example, aLevel 1 (L1) internal cache, or multiple levels of internal cache. Insome embodiments, the system may include a combination of an internalcache and an external cache that is external to the core and/or theprocessor. Alternatively, all of the cache may be external to the coreand/or the processor.

FIG. 5B is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipelineimplemented by processor 500 of FIG. 5A according to some embodiments ofthe disclosure. The solid lined boxes in FIG. 5B illustrate an in-orderpipeline, while the dashed lined boxes illustrates a register renaming,out-of-order issue/execution pipeline. In FIG. 5B, a processor 500 as apipeline includes a fetch stage 502, a length decode stage 504, a decodestage 506, an allocation stage 508, a renaming stage 510, a scheduling(also known as a dispatch or issue) stage 512, a register read/memoryread stage 514, an execute stage 516, a write back/memory write stage518, an exception handling stage 522, and a commit stage 524. In someembodiments, the ordering of stages 502-524 may be different thanillustrated and are not limited to the specific ordering shown in FIG.5B.

FIG. 6 illustrates a block diagram of the micro-architecture for aprocessor 600 (e.g., processing device 100) that includes hybrid coresin accordance with one embodiment of the disclosure. In someembodiments, an instruction in accordance with one embodiment can beimplemented to operate on data elements having sizes of byte, word,doubleword, quadword, etc., as well as datatypes, such as single anddouble precision integer and floating point datatypes. In one embodimentthe in-order front end 601 is the part of the processor 600 that fetchesinstructions to be executed and prepares them to be used later in theprocessor pipeline.

The front end 601 may include several units. In one embodiment, theinstruction prefetcher 626 fetches instructions from memory and feedsthem to an instruction decoder 628 which in turn decodes or interpretsthem. For example, in one embodiment, the decoder decodes a receivedinstruction into one or more operations called “micro-instructions” or“micro-operations” (also called micro op or uops) that the machine canexecute. In other embodiments, the decoder parses the instruction intoan opcode and corresponding data and control fields that are used by themicro-architecture to perform operations in accordance with oneembodiment. In one embodiment, the trace cache 630 takes decoded uopsand assembles them into program ordered sequences or traces in the uopqueue 634 for execution. When the trace cache 630 encounters a complexinstruction, the microcode ROM 632 provides the uops needed to completethe operation.

Some instructions are converted into a single micro-op, whereas othersneed several micro-ops to complete the full operation. In oneembodiment, if more than four micro-ops are needed to complete aninstruction, the decoder 628 accesses the microcode ROM 632 to do theinstruction. For one embodiment, an instruction can be decoded into asmall number of micro ops for processing at the instruction decoder 628.In another embodiment, an instruction can be stored within the microcodeROM 632 should a number of micro-ops be needed to accomplish theoperation. The trace cache 630 refers to an entry point programmablelogic array (PLA) to determine a correct micro-instruction pointer forreading the micro-code sequences to complete one or more instructions inaccordance with one embodiment from the micro-code ROM 632. After themicrocode ROM 632 finishes sequencing micro-ops for an instruction, thefront end 601 of the machine resumes fetching micro-ops from the tracecache 630.

The out-of-order execution engine 603 is where the instructions areprepared for execution. The out-of-order execution logic has a number ofbuffers to smooth out and re-order the flow of instructions to optimizeperformance as they go down the pipeline and get scheduled forexecution. The allocator logic allocates the machine buffers andresources that each uop needs in order to execute. The register renaminglogic renames logic registers onto entries in a register file. Theallocator also allocates an entry for each uop in one of the two uopqueues, one for memory operations and one for non-memory operations, infront of the instruction schedulers: memory scheduler, fast scheduler602, slow/general floating point scheduler 604, and simple floatingpoint scheduler 606. The uop schedulers 602, 604, 606, determine when auop is ready to execute based on the readiness of their dependent inputregister operand sources and the availability of the execution resourcesthe uops need to complete their operation. The fast scheduler 602 of oneembodiment can schedule on each half of the main clock cycle while theother schedulers can only schedule once per main processor clock cycle.The schedulers arbitrate for the dispatch ports to schedule uops forexecution.

Register files 608, 610, sit between the schedulers 602, 604, 606, andthe execution units 612, 614, 616, 618, 620, 622, 624 in the executionblock 611. There is a separate register file 608, 610, for integer andfloating point operations, respectively. Each register file 608, 610, ofone embodiment also includes a bypass network that can bypass or forwardjust completed results that have not yet been written into the registerfile to new dependent uops. The integer register file 608 and thefloating point register file 610 are also capable of communicating datawith the other. For one embodiment, the integer register file 608 issplit into two separate register files, one register file for the loworder 32 bits of data and a second register file for the high order 32bits of data. The floating point register file 610 of one embodiment has128 bit wide entries because floating point instructions typically haveoperands from 64 to 128 bits in width.

The execution block 611 contains the execution units 612, 614, 616, 618,620, 622, 624, where the instructions are actually executed. Thissection includes the register files 608, 610, that store the integer andfloating point data operand values that the micro-instructions need toexecute. The processor 600 of one embodiment is comprised of a number ofexecution units: address generation unit (AGU) 612, AGU 614, fast ALU616, fast ALU 618, slow ALU 620, floating point ALU 622, floating pointmove unit 624. For one embodiment, the floating point execution blocks622, 624, execute floating point, MMX, SIMD, and SSE, or otheroperations. The floating point ALU 622 of one embodiment includes a 64bit by 64 bit floating point divider to execute divide, square root, andremainder micro-ops. For embodiments of the present disclosure,instructions involving a floating point value may be handled with thefloating point hardware.

In one embodiment, the ALU operations go to the high-speed ALU executionunits 616, 618. The fast ALUs 616, 618, of one embodiment can executefast operations with an effective latency of half a clock cycle. For oneembodiment, most complex integer operations go to the slow ALU 620 asthe slow ALU 620 includes integer execution hardware for long latencytype of operations, such as a multiplier, shifts, flag logic, and branchprocessing. Memory load/store operations are executed by the AGUs 612,614. For one embodiment, the integer ALUs 616, 618, 620, are describedin the context of performing integer operations on 64 bit data operands.In alternative embodiments, the ALUs 616, 618, 620, can be implementedto support a variety of data bits including 16, 32, 128, 256, etc.Similarly, the floating point units 622, 624, can be implemented tosupport a range of operands having bits of various widths. For oneembodiment, the floating point units 622, 624, can operate on 128 bitswide packed data operands in conjunction with SIMD and multimediainstructions.

In one embodiment, the uops schedulers 602, 604, 606, dispatch dependentoperations before the parent load has finished executing. As uops arespeculatively scheduled and executed in processor 600, the processor 600also includes logic to handle memory misses. If a data load misses inthe data cache, there can be dependent operations in flight in thepipeline that have left the scheduler with temporarily incorrect data. Areplay mechanism tracks and re-executes instructions that use incorrectdata. Only the dependent operations need to be replayed and theindependent ones are allowed to complete. The schedulers and replaymechanism of one embodiment of a processor are also designed to catchinstruction sequences for text string comparison operations.

The processor 600 also includes logic to implement store addressprediction for memory disambiguation according to embodiments of thedisclosure. In one embodiment, the execution block 611 of processor 600may include a store address predictor (not shown) for implementing storeaddress prediction for memory disambiguation.

The term “registers” may refer to the on-board processor storagelocations that are used as part of instructions to identify operands. Inother words, registers may be those that are usable from the outside ofthe processor (from a programmer's perspective). However, the registersof an embodiment should not be limited in meaning to a particular typeof circuit. Rather, a register of an embodiment is capable of storingand providing data, and performing the functions described herein. Theregisters described herein can be implemented by circuitry within aprocessor using any number of different techniques, such as dedicatedphysical registers, dynamically allocated physical registers usingregister renaming, combinations of dedicated and dynamically allocatedphysical registers, etc. In one embodiment, integer registers storethirty-two bit integer data. A register file of one embodiment alsocontains eight multimedia SIMD registers for packed data.

For the discussions below, the registers are understood to be dataregisters designed to hold packed data, such as 64 bits wide MMX™registers (also referred to as ‘mm’ registers in some instances) inmicroprocessors enabled with MMX technology from Intel Corporation ofSanta Clara, Calif. These MMX registers, available in both integer andfloating point forms, can operate with packed data elements thataccompany SIMD and SSE instructions. Similarly, 128 bits wide XMMregisters relating to SSE2, SSE3, SSE4, or beyond (referred togenerically as “SSEx”) technology can also be used to hold such packeddata operands. In one embodiment, in storing packed data and integerdata, the registers do not need to differentiate between the two datatypes. In one embodiment, integer and floating point are eithercontained in the same register file or different register files.Furthermore, in one embodiment, floating point and integer data may bestored in different registers or the same registers.

Referring now to FIG. 7, shown is a block diagram illustrating a system700 in which an embodiment of the disclosure may be used. As shown inFIG. 7, multiprocessor system 700 is a point-to-point interconnectsystem, and includes a first processor 770 and a second processor 780coupled via a point-to-point interconnect 750. While shown with only twoprocessors 770, 780, it is to be understood that the scope ofembodiments of the disclosure is not so limited. In other embodiments,one or more additional processors may be present in a given processor.In one embodiment, the multiprocessor system 700 may implement hybridcores as described herein.

Processors 770 and 780 are shown including integrated memory controllerunits 772 and 782, respectively. Processor 770 also includes as part ofits bus controller units point-to-point (P-P) interfaces 776 and 778;similarly, second processor 780 includes P-P interfaces 786 and 788.Processors 770, 780 may exchange information via a point-to-point (P-P)interface 750 using P-P interface circuits 778, 788. As shown in FIG. 7,IMCs 772 and 782 couple the processors to respective memories, namely amemory 732 and a memory 734, which may be portions of main memorylocally attached to the respective processors.

Processors 770, 780 may each exchange information with a chipset 790 viaindividual P-P interfaces 752, 754 using point to point interfacecircuits 776, 794, 786, 798. Chipset 790 may also exchange informationwith a high-performance graphics circuit 738 via a high-performancegraphics interface 739.

A shared cache (not shown) may be included in either processor oroutside of both processors, yet connected with the processors via P-Pinterconnect, such that either or both processors' local cacheinformation may be stored in the shared cache if a processor is placedinto a low power mode.

Chipset 790 may be coupled to a first bus 716 via an interface 796. Inone embodiment, first bus 716 may be a Peripheral Component Interconnect(PCI) bus, or a bus such as a PCI Express bus or another thirdgeneration I/O interconnect bus, although the scope of the presentdisclosure is not so limited.

As shown in FIG. 7, various I/O devices 714 may be coupled to first bus716, along with a bus bridge 718 which couples first bus 716 to a secondbus 720. In one embodiment, second bus 720 may be a low pin count (LPC)bus. Various devices may be coupled to second bus 720 including, forexample, a keyboard and/or mouse 722, communication devices 727 and astorage unit 728 such as a disk drive or other mass storage device whichmay include instructions/code and data 730, in one embodiment. Further,an audio I/O 724 may be coupled to second bus 720. Note that otherarchitectures are possible. For example, instead of the point-to-pointarchitecture of FIG. 7, a system may implement a multi-drop bus or othersuch architecture.

Referring now to FIG. 8, shown is a block diagram of a system 800 inwhich one embodiment of the disclosure may operate. The system 800 mayinclude one or more processors 810, 815, which are coupled to graphicsmemory controller hub (GMCH) 820. The optional nature of additionalprocessors 815 is denoted in FIG. 8 with broken lines. In oneembodiment, processors 810, 815 implement hybrid cores according toembodiments of the disclosure.

Each processor 810, 815 may be some version of the circuit, integratedcircuit, processor, and/or silicon integrated circuit as describedabove. However, it should be noted that it is unlikely that integratedgraphics logic and integrated memory control units would exist in theprocessors 810, 815. FIG. 8 illustrates that the GMCH 820 may be coupledto a memory 840 that may be, for example, a dynamic random access memory(DRAM). The DRAM may, for at least one embodiment, be associated with anon-volatile cache.

The GMCH 820 may be a chipset, or a portion of a chipset. The GMCH 820may communicate with the processor(s) 810, 815 and control interactionbetween the processor(s) 810, 815 and memory 840. The GMCH 820 may alsoact as an accelerated bus interface between the processor(s) 810, 815and other elements of the system 800. For at least one embodiment, theGMCH 820 communicates with the processor(s) 810, 815 via a multi-dropbus, such as a frontside bus (FSB) 895.

Furthermore, GMCH 820 is coupled to a display 845 (such as a flat panelor touchscreen display). GMCH 820 may include an integrated graphicsaccelerator. GMCH 820 is further coupled to an input/output (I/O)controller hub (ICH) 850, which may be used to couple various peripheraldevices to system 800. Shown for example in the embodiment of FIG. 8 isan external graphics device 860, which may be a discrete graphicsdevice, coupled to ICH 850, along with another peripheral device 870.

Alternatively, additional or different processors may also be present inthe system 800. For example, additional processor(s) 815 may includeadditional processors(s) that are the same as processor 810, additionalprocessor(s) that are heterogeneous or asymmetric to processor 810,accelerators (such as, e.g., graphics accelerators or digital signalprocessing (DSP) units), field programmable gate arrays, or any otherprocessor. There can be a variety of differences between theprocessor(s) 810, 815 in terms of a spectrum of metrics of meritincluding architectural, micro-architectural, thermal, power consumptioncharacteristics, and the like. These differences may effectivelymanifest themselves as asymmetry and heterogeneity amongst theprocessors 810, 815. For at least one embodiment, the various processors810, 815 may reside in the same die package.

Referring now to FIG. 9, shown is a block diagram of a system 900 inwhich an embodiment of the disclosure may operate. FIG. 9 illustratesprocessors 970, 980. In one embodiment, processors 970, 980 mayimplement hybrid cores as described above. Processors 970, 980 mayinclude integrated memory and I/O control logic (“CL”) 972 and 982,respectively and intercommunicate with each other via point-to-pointinterconnect 950 between point-to-point (P-P) interfaces 978 and 988respectively. Processors 970, 980 each communicate with chipset 990 viapoint-to-point interconnects 952 and 954 through the respective P-Pinterfaces 976 to 994 and 986 to 998 as shown. For at least oneembodiment, the CL 972, 982 may include integrated memory controllerunits. CLs 972, 982 may include I/O control logic. As depicted, memories932, 934 coupled to CLs 972, 982 and I/O devices 914 are also coupled tothe control logic 972, 982. Legacy I/O devices 915 are coupled to thechipset 990 via interface 996.

Embodiments may be implemented in many different system types. FIG. 10is a block diagram of a SoC 1000 in accordance with an embodiment of thepresent disclosure. Dashed lined boxes are optional features on moreadvanced SoCs. In FIG. 10, an interconnect unit(s) 1012 is coupled to:an application processor 1020 which includes a set of one or more cores1002A-N and shared cache unit(s) 1006; a system agent unit 1010; a buscontroller unit(s) 1016; an integrated memory controller unit(s) 1014; aset or one or more media processors 1018 which may include integratedgraphics logic 1008, an image processor 1024 for providing still and/orvideo camera functionality, an audio processor 1026 for providinghardware audio acceleration, and a video processor 1028 for providingvideo encode/decode acceleration; an static random access memory (SRAM)unit 1030; a direct memory access (DMA) unit 1032; and a display unit1040 for coupling to one or more external displays. In one embodiment, amemory module may be included in the integrated memory controllerunit(s) 1014. In another embodiment, the memory module may be includedin one or more other components of the SoC 1000 that may be used toaccess and/or control a memory. The application processor 1020 mayinclude a store address predictor for implementing hybrid cores asdescribed in embodiments herein.

The memory hierarchy includes one or more levels of cache within thecores, a set or one or more shared cache units 1006, and external memory(not shown) coupled to the set of integrated memory controller units1014. The set of shared cache units 1006 may include one or moremid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), orother levels of cache, a last level cache (LLC), and/or combinationsthereof.

In some embodiments, one or more of the cores 1002A-N are capable ofmultithreading. The system agent 1010 includes those componentscoordinating and operating cores 1002A-N. The system agent unit 1010 mayinclude for example a power control unit (PCU) and a display unit. ThePCU may be or include logic and components needed for regulating thepower state of the cores 1002A-N and the integrated graphics logic 1008.The display unit is for driving one or more externally connecteddisplays.

The cores 1002A-N may be homogenous or heterogeneous in terms ofarchitecture and/or instruction set. For example, some of the cores1002A-N may be in order while others are out-of-order. As anotherexample, two or more of the cores 1002A-N may be capable of executionthe same instruction set, while others may be capable of executing onlya subset of that instruction set or a different instruction set.

The application processor 1020 may be a general-purpose processor, suchas a Core™ i3, i5, i7, 2 Duo and Quad, Xeon™, Itanium™, Atom™ or Quark™processor, which are available from Intel™ Corporation, of Santa Clara,Calif. Alternatively, the application processor 1020 may be from anothercompany, such as ARM Holdings™, Ltd, MIPS™, etc. The applicationprocessor 1020 may be a special-purpose processor, such as, for example,a network or communication processor, compression engine, graphicsprocessor, co-processor, embedded processor, or the like. Theapplication processor 1020 may be implemented on one or more chips. Theapplication processor 1020 may be a part of and/or may be implemented onone or more substrates using any of a number of process technologies,such as, for example, BiCMOS, CMOS, or NMOS.

FIG. 11 is a block diagram of an embodiment of a system on-chip (SoC)design in accordance with the present disclosure. As a specificillustrative example, SoC 1100 is included in user equipment (UE). Inone embodiment, UE refers to any device to be used by an end-user tocommunicate, such as a hand-held phone, smartphone, tablet, ultra-thinnotebook, notebook with broadband adapter, or any other similarcommunication device. Often a UE connects to a base station or node,which potentially corresponds in nature to a mobile station (MS) in aGSM network.

Here, SOC 1100 includes 2 cores—1106 and 1107. Cores 1106 and 1107 mayconform to an Instruction Set Architecture, such as an Intel®Architecture Core™-based processor, an Advanced Micro Devices, Inc.(AMD) processor, a MIPS-based processor, an ARM-based processor design,or a customer thereof, as well as their licensees or adopters. Cores1106 and 1107 are coupled to cache control 1108 that is associated withbus interface unit 1109 and L2 cache 1110 to communicate with otherparts of system 1100. Interconnect 1111 includes an on-chipinterconnect, such as an IOSF, AMBA, or other interconnect discussedabove, which potentially implements one or more aspects of the describeddisclosure. In one embodiment, cores 1106, 1107 may implement hybridcores as described in embodiments herein.

Interconnect 1111 provides communication channels to the othercomponents, such as a Subscriber Identity Module (SIM) 1130 to interfacewith a SIM card, a boot ROM 1135 to hold boot code for execution bycores 1106 and 1107 to initialize and boot SoC 1100, a SDRAM controller1140 to interface with external memory (e.g. DRAM 1160), a flashcontroller 1145 to interface with non-volatile memory (e.g. Flash 1165),a peripheral control 1150 (e.g. Serial Peripheral Interface) tointerface with peripherals, video codecs 1120 and Video interface 1125to display and receive input (e.g. touch enabled input), GPU 1115 toperform graphics related computations, etc. Any of these interfaces mayincorporate aspects of the disclosure described herein. In addition, thesystem 1100 illustrates peripherals for communication, such as aBluetooth module 1170, 3G modem 1175, GPS 1180, and Wi-Fi 1185.

FIG. 12 illustrates a diagrammatic representation of a machine in theexample form of a computer system 1200 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a LAN, an intranet, an extranet, or the Internet. Themachine may operate in the capacity of a server or a client device in aclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The computer system 1200 includes a processing device 1202, a mainmemory 1204 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) (such as synchronous DRAM (SDRAM) or DRAM (RDRAM),etc.), a static memory 1206 (e.g., flash memory, static random accessmemory (SRAM), etc.), and a data storage device 1218, which communicatewith each other via a bus 1230.

Processing device 1202 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device may be complex instruction setcomputing (CISC) microprocessor, reduced instruction set computer (RISC)microprocessor, very long instruction word (VLIW) microprocessor, orprocessor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 1202may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. In one embodiment, processing device 1202 may include oneor more processing cores. The processing device 1202 is configured toexecute the processing logic 1226 for performing the operations andsteps discussed herein. For example, processing logic 1226 may performoperations as described in FIG. 4.

The computer system 1200 may further include a network interface device1208 communicably coupled to a network 1220. The computer system 1200also may include a video display unit 1210 (e.g., a liquid crystaldisplay (LCD) or a cathode ray tube (CRT)), an alphanumeric input device1212 (e.g., a keyboard), a cursor control device 1214 (e.g., a mouse),and a signal generation device 1216 (e.g., a speaker). Furthermore,computer system 1200 may include a graphics processing unit 1222, avideo processing unit 1228, and an audio processing unit 1232.

The data storage device 1218 may include a machine-accessible storagemedium 1224 on which is stored software 1226 implementing any one ormore of the methodologies of functions described herein, such asimplementing store address prediction for memory disambiguation asdescribed above. The software 1226 may also reside, completely or atleast partially, within the main memory 1204 as instructions 1226 and/orwithin the processing device 1202 as processing logic 1226 duringexecution thereof by the computer system 1200; the main memory 1204 andthe processing device 1202 also constituting machine-accessible storagemedia.

The machine-readable storage medium 1224 may also be used to storeinstructions 1226 implementing store address prediction for hybrid coressuch as described according to embodiments of the disclosure. While themachine-accessible storage medium 1128 is shown in an example embodimentto be a single medium, the term “machine-accessible storage medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-accessible storage medium” shall also be taken to include anymedium that is capable of storing, encoding or carrying a set ofinstruction for execution by the machine and that cause the machine toperform any one or more of the methodologies of the present disclosure.The term “machine-accessible storage medium” shall accordingly be takento include, but not be limited to, solid-state memories, and optical andmagnetic media.

The following examples pertain to further embodiments.

Example 1 is a processing device comprising: 1) compression circuitryto: a) determine a compression configuration to compress source data; b)generate a checksum of the source data in an uncompressed state; c)compress the source data into at least one block based on thecompression configuration, wherein the at least one block comprises: aplurality of sub-blocks, wherein the plurality of sub-block includes apredetermined size; a block header corresponding to the plurality ofsub-blocks; and 2) decompression circuitry coupled to the compressioncircuitry, wherein the decompression circuitry to: while not outputtinga decompressed data stream of the source data: a) generate indexinformation corresponding to the plurality of sub-blocks; b) in responseto generating the index information, generate a checksum of thecompressed source data associated with the plurality of sub-blocks; andc) determine whether the checksum of the source data in the uncompressedformat matches the checksum of the compressed source data.

In Example 2, the processing device of Example 1, wherein thedecompression circuitry is further to: in response to determining thatthe checksum of the source data in the uncompressed data format matchesthe checksum of the compressed source data, verify that the source datawas properly compressed.

In Example 3, the processing device of Example 1, wherein thedecompression circuitry is further to: in response to determining thatthe checksum of the source data in the uncompressed data format does notmatch the checksum of the compressed source data, verify that the sourcedata was not properly compressed.

In Example 4, the processing device of Example 1, wherein thedecompression circuitry is further to: determine whether source data iscompressed into the at least one block based on the compressionconfiguration.

In Example 5, the processing device of Example 1, wherein the block is aDeflate block.

In Example 6, the processing device of Example 1, wherein the indexinformation comprises bit offset of each of the plurality of sub-blocks.

In Example 7, the processing device of Example 1, wherein thedecompression circuitry is further to: generate a cumulative checksum ofthe compressed source data at a bit offset of each of the plurality ofsub-blocks.

In Example 8, the processing device of Example 1, wherein a sub-block ofthe plurality of sub-blocks comprises history information fordecompressing all of the data in the sub-block, the history informationnot including information for other sub-blocks of the plurality ofsub-blocks.

In Example 9, the processing device of Example 1, wherein thedecompression circuitry is further to: provide for random access of asingle sub-block of the plurality of sub-blocks by receiving a requestfor the single sub-block and decompressing the requested singlesub-block while not decompressing other sub-blocks of the plurality ofsub-blocks.

Various implementations may have different combinations of thestructural features described above. For instance, all optional featuresof the processors and methods described above may also be implementedwith respect to a system described herein and specifics in the examplesmay be used anywhere in one or more implementations.

Example 10 is a processing system comprising: 1) a core, 2) memorycoupled to the core, 3) compression circuitry to: a) determine acompression configuration to compress source data; b) generate achecksum of the source data in an uncompressed state; c) compress thesource data into at least one block based on the compressionconfiguration, wherein the at least one block comprises: a plurality ofsub-blocks, wherein the plurality of sub-block includes a predeterminedsize; a block header corresponding to the plurality of sub-blocks; and4) decompression circuitry coupled to the compression circuitry, whereinthe decompression circuitry to: while not outputting a decompressed datastream of the source data: a) generate index information correspondingto the plurality of sub-blocks; b) in response to generating the indexinformation, generate a checksum of the compressed source dataassociated with the plurality of sub-blocks; and c) determine whetherthe checksum of the source data in the uncompressed format matches thechecksum of the compressed source data.

In Example 11, the processing system of Example 10, wherein thedecompression circuitry is further to: in response to determining thatthe checksum of the source data in the uncompressed data format matchesthe checksum of the compressed source data, verify that the source datawas properly compressed.

In Example 12, the processing system of Example 10, wherein thedecompression circuitry is further to: in response to determining thatthe checksum of the source data in the uncompressed data format does notmatch the checksum of the compressed source data, verify that the sourcedata was not properly compressed.

In Example 13, the processing system of Example 10, wherein thedecompression circuitry is further to: determine whether source data iscompressed into the at least one block based on the compressionconfiguration.

In Example 14, the processing system of Example 10, wherein the block isa Deflate block.

In Example 15, the processing system of Example 10, wherein the indexinformation comprises bit offset of each of the plurality of sub-blocks.

In Example 16, the processing system of Example 10, wherein thedecompression circuitry is further to: generate a cumulative checksum ofthe compressed source data at a bit offset of each of the plurality ofsub-blocks.

In Example 17, the processing system of Example 10, wherein a sub-blockof the plurality of sub-blocks comprises history information fordecompressing all of the data in the sub-block, the history informationnot including information for other sub-blocks of the plurality ofsub-blocks.

In Example 18, the processing system of Example 10, wherein thedecompression circuitry is further to: provide for random access of asingle sub-block of the plurality of sub-blocks by receiving a requestfor the single sub-block and decompressing the requested singlesub-block while not decompressing other sub-blocks of the plurality ofsub-blocks.

Various implementations may have different combinations of thestructural features described above. For instance, all optional featuresof the processors and methods described above may also be implementedwith respect to a system described herein and specifics in the examplesmay be used anywhere in one or more implementations.

In Example 19, is a non-transitory computer-readable medium storinginstructions, which when executed by a processor, cause the processor toexecute a plurality of logic operations comprising: determine acompression configuration to compress source data; generate a checksumof the source data in an uncompressed state; compress the source datainto at least one block based on the compression configuration, whereinthe at least one block comprises: a plurality of sub-blocks, wherein theplurality of sub-block includes a predetermined size; and a block headercorresponding to the plurality of sub-blocks; and while not outputting adecompressed data stream of the source data: generate index informationcorresponding to the plurality of sub-blocks; in response to generatingthe index information, generate a checksum of the compressed source dataassociated with the plurality of sub-blocks; and determine whether thechecksum of the source data in the uncompressed format matches thechecksum of the compressed source data.

In Example 20, the non-transitory computer-readable medium of Example19, in response to determining that the checksum of the source data inthe uncompressed data format matches the checksum of the compressedsource data, verifying that the source data was properly compressed.

In Example 21, the non-transitory computer-readable medium of Example19, determining whether source data is compressed into the at least oneblock based on the compression configuration.

In Example 22, the non-transitory computer-readable medium of Example19, generating a cumulative checksum of the compressed source data at abit offset of each of the plurality of sub-blocks.

In Example 23, the non-transitory computer-readable medium of Example19, providing for random access of a single sub-block of the pluralityof sub-blocks by receiving a request for the single sub-block anddecompressing the requested single sub-block while not decompressingother sub-blocks of the plurality of sub-blocks.

Various implementations may have different combinations of thestructural features described above. For instance, all optional featuresof the processors and methods described above may also be implementedwith respect to a system described herein and specifics in the examplesmay be used anywhere in one or more implementations.

Example 24 is an apparatus comprising 1) means for determining acompression configuration to compress source data; generate a checksumof the source data in an uncompressed state; 2) means for compressingthe source data into at least one block based on the compressionconfiguration; and while not outputting a decompressed data stream ofthe source data: 3) means for generating index information correspondingto the plurality of sub-blocks; in response to generating the indexinformation, 4) means for generating a checksum of the compressed sourcedata associated with the plurality of sub-blocks; and 5) means fordetermining whether the checksum of the source data in the uncompressedformat matches the checksum of the compressed source data.

A design may go through various stages, from creation to simulation tofabrication. Data representing a design may represent the design in anumber of manners. First, as is useful in simulations, the hardware maybe represented using a hardware description language or anotherfunctional description language. Additionally, a circuit level modelwith logic and/or transistor gates may be produced at some stages of thedesign process. Furthermore, most designs, at some stage, reach a levelof data representing the physical placement of various devices in thehardware model. In the case where conventional semiconductor fabricationtechniques are used, the data representing the hardware model may be thedata specifying the presence or absence of various features on differentmask layers for masks used to produce the integrated circuit. In anyrepresentation of the design, the data may be stored in any form of amachine readable medium. A memory or a magnetic or optical storage suchas a disc may be the machine readable medium to store informationtransmitted via optical or electrical wave modulated or otherwisegenerated to transmit such information. When an electrical carrier waveindicating or carrying the code or design is transmitted, to the extentthat copying, buffering, or re-transmission of the electrical signal isperformed, a new copy is made. Thus, a communication provider or anetwork provider may store on a tangible, machine-readable medium, atleast temporarily, an article, such as information encoded into acarrier wave, embodying techniques of embodiments of the presentdisclosure.

A module as used herein refers to any combination of hardware, software,and/or firmware. As an example, a module includes hardware, such as amicro-controller, associated with a non-transitory medium to store codeadapted to be executed by the micro-controller. Therefore, reference toa module, in one embodiment, refers to the hardware, which isspecifically configured to recognize and/or execute the code to be heldon a non-transitory medium. Furthermore, in another embodiment, use of amodule refers to the non-transitory medium including the code, which isspecifically adapted to be executed by the microcontroller to performpredetermined operations. And as can be inferred, in yet anotherembodiment, the term module (in this example) may refer to thecombination of the microcontroller and the non-transitory medium. Oftenmodule boundaries that are illustrated as separate commonly vary andpotentially overlap. For example, a first and a second module may sharehardware, software, firmware, or a combination thereof, whilepotentially retaining some independent hardware, software, or firmware.In one embodiment, use of the term logic includes hardware, such astransistors, registers, or other hardware, such as programmable logicdevices.

Use of the phrase ‘configured to,’ in one embodiment, refers toarranging, putting together, manufacturing, offering to sell, importingand/or designing an apparatus, hardware, logic, or element to perform adesignated or determined task. In this example, an apparatus or elementthereof that is not operating is still ‘configured to’ perform adesignated task if it is designed, coupled, and/or interconnected toperform said designated task. As a purely illustrative example, a logicgate may provide a 0 or a 1 during operation. But a logic gate‘configured to’ provide an enable signal to a clock does not includeevery potential logic gate that may provide a 1 or 0. Instead, the logicgate is one coupled in some manner that during operation the 1 or 0output is to enable the clock. Note once again that use of the term‘configured to’ does not require operation, but instead focus on thelatent state of an apparatus, hardware, and/or element, where in thelatent state the apparatus, hardware, and/or element is designed toperform a particular task when the apparatus, hardware, and/or elementis operating.

Furthermore, use of the phrases ‘to,’ ‘capable of/to,’ and/or ‘operableto,’ in one embodiment, refers to some apparatus, logic, hardware,and/or element designed in such a way to enable use of the apparatus,logic, hardware, and/or element in a specified manner. Note as abovethat use of ‘to,’ ‘capable of/to,’ and/or ‘operable to,’ in oneembodiment, refers to the latent state of an apparatus, logic, hardware,and/or element, where the apparatus, logic, hardware, and/or element isnot operating but is designed in such a manner to enable use of anapparatus in a specified manner.

A value, as used herein, includes any known representation of a number,a state, a logical state, or a binary logical state. Often, the use oflogic levels, logic values, or logical values is also referred to as 1'sand 0's, which simply represents binary logic states. For example, a 1refers to a high logic level and 0 refers to a low logic level. In oneembodiment, a storage cell, such as a transistor or flash cell, may becapable of holding a single logical value or multiple logical values.However, other representations of values in computer systems have beenused. For example the decimal number ten may also be represented as abinary value of 910 and a hexadecimal letter A. Therefore, a valueincludes any representation of information capable of being held in acomputer system.

Moreover, states may be represented by values or portions of values. Asan example, a first value, such as a logical one, may represent adefault or initial state, while a second value, such as a logical zero,may represent a non-default state. In addition, the terms reset and set,in one embodiment, refer to a default and an updated value or state,respectively. For example, a default value potentially includes a highlogical value, i.e. reset, while an updated value potentially includes alow logical value, i.e. set. Note that any combination of values may beutilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code setforth above may be implemented via instructions or code stored on amachine-accessible, machine readable, computer accessible, or computerreadable medium which are executable by a processing element. Anon-transitory machine-accessible/readable medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formreadable by a machine, such as a computer or electronic system. Forexample, a non-transitory machine-accessible medium includesrandom-access memory (RAM), such as static RAM (SRAM) or dynamic RAM(DRAM); ROM; magnetic or optical storage medium; flash memory devices;electrical storage devices; optical storage devices; acoustical storagedevices; other form of storage devices for holding information receivedfrom transitory (propagated) signals (e.g., carrier waves, infraredsignals, digital signals); etc., which are to be distinguished from thenon-transitory mediums that may receive information there from.

Instructions used to program logic to perform embodiments of thedisclosure may be stored within a memory in the system, such as DRAM,cache, flash memory, or other storage. Furthermore, the instructions canbe distributed via a network or by way of other computer readable media.Thus a machine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer), but is not limited to, floppy diskettes, optical disks,Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks,Read-Only Memory (ROMs), Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), magnetic or optical cards, flashmemory, or a tangible, machine-readable storage used in the transmissionof information over the Internet via electrical, optical, acoustical orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Accordingly, the computer-readablemedium includes any type of tangible machine-readable medium suitablefor storing or transmitting electronic instructions or information in aform readable by a machine (e.g., a computer).

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present disclosure. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

In the foregoing specification, a detailed description has been givenwith reference to specific exemplary embodiments. It will, however, beevident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the disclosure asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense. Furthermore, the foregoing use of embodiment andother exemplarily language does not necessarily refer to the sameembodiment or the same example, but may refer to different and distinctembodiments, as well as potentially the same embodiment.

1. A processing device comprising: compression circuitry to: determine acompression configuration to compress source data; generate a checksumof the source data in an uncompressed state; compress the source datainto at least one block based on the compression configuration, whereinthe at least one block comprises: a plurality of sub-blocks, wherein theplurality of sub-block includes a predetermined size; a block headercorresponding to the plurality of sub-blocks; and decompressioncircuitry coupled to the compression circuitry, wherein thedecompression circuitry to: while not outputting a decompressed datastream of the source data: generate index information corresponding tothe plurality of sub-blocks; in response to generating the indexinformation, generate a checksum of the compressed source dataassociated with the plurality of sub-blocks; and determine whether thechecksum of the source data in the uncompressed format matches thechecksum of the compressed source data.
 2. The processing device ofclaim 1, wherein the decompression circuitry is further to: in responseto determining that the checksum of the source data in the uncompresseddata format matches the checksum of the compressed source data, verifythat the source data was properly compressed.
 3. The processing deviceof claim 1, wherein the decompression circuitry is further to: inresponse to determining that the checksum of the source data in theuncompressed data format does not match the checksum of the compressedsource data, verify that the source data was not properly compressed. 4.The processing device of claim 1, wherein the decompression circuitry isfurther to: determine whether source data is compressed into the atleast one block based on the compression configuration.
 5. Theprocessing device of claim 1, wherein the block is a Deflate block. 6.The processing device of claim 1, wherein the index informationcomprises bit offset of each of the plurality of sub-blocks.
 7. Theprocessing device of claim 1, wherein the decompression circuitry isfurther to: generate a cumulative checksum of the compressed source dataat a bit offset of each of the plurality of sub-blocks.
 8. Theprocessing device of claim 1, wherein a sub-block of the plurality ofsub-blocks comprises history information for decompressing all of thedata in the sub-block, the history information not including informationfor other sub-blocks of the plurality of sub-blocks.
 9. The processingdevice of claim 1, wherein the decompression circuitry is further to:provide for random access of a single sub-block of the plurality ofsub-blocks by receiving a request for the single sub-block anddecompressing the requested single sub-block while not decompressingother sub-blocks of the plurality of sub-blocks.
 10. A processing systemcomprising: a core; memory coupled to the core; compression circuitrycoupled to the core and memory, the compression circuitry to: determinea compression configuration to compress source data; generate a checksumof the source data in an uncompressed state; compress the source datainto at least one block based on the compression configuration, whereinthe at least one block comprises: a plurality of sub-blocks, wherein theplurality of sub-block includes a predetermined size; and a block headercorresponding to the plurality of sub-blocks; and decompressioncircuitry coupled to the compression circuitry, the core and memory,wherein the decompression circuitry to: while not outputting adecompressed data stream of the source data: generate index informationcorresponding to the plurality of sub-blocks; in response to generatingthe index information, generate a checksum of the compressed source dataassociated with the plurality of sub-blocks; and determine whether thechecksum of the source data in the uncompressed format matches thechecksum of the compressed source data.
 11. The processing system ofclaim 10, wherein the decompression circuitry is further to: in responseto determining that the first checksum of the source data in theuncompressed data format matches the second checksum of the uncompresseddata from the compressed source data, verify that the source data wasproperly compressed.
 12. The processing system of claim 10, wherein thedecompression circuitry is further to: in response to determining thatthe first checksum of the source data in the uncompressed data formatdoes not match the second checksum of the uncompressed data from thecompressed source data, verify that the source data was not properlycompressed.
 13. The processing system of claim 10, wherein thedecompression circuitry is further to: determine whether source data iscompressed into the at least one block based on the compressionconfiguration.
 14. The processing system of claim 10, wherein the blockis a Deflate block.
 15. The processing system of claim 10, wherein theindex information comprises bit offset of each of the plurality ofsub-blocks.
 16. The processing system of claim 10, wherein thedecompression circuitry is further to: generate a cumulative checksum ofthe compressed source data at a bit offset of each of the plurality ofsub-blocks.
 17. The processing system of claim 10, wherein a sub-blockof the plurality of sub-blocks comprises history information fordecompressing all of the data in the sub-block, the history informationnot including information for other sub-blocks of the plurality ofsub-blocks.
 18. The processing system of claim 10, wherein thedecompression circuitry is further to: provide for random access of asingle sub-block of the plurality of sub-blocks by receiving a requestfor the single sub-block and decompressing the requested singlesub-block while not decompressing other sub-blocks of the plurality ofsub-blocks.
 19. A method comprising: determining a compressionconfiguration to compress source data; generating a first checksum ofthe source data in an uncompressed state; compressing the source datainto at least one block based on the compression configuration, whereinthe at least one block comprises: a plurality of sub-blocks, wherein theplurality of sub-block includes a predetermined size; and a block headercorresponding to the plurality of sub-blocks; and while not outputting adecompressed data stream of the source data: generating indexinformation corresponding to the plurality of sub-blocks; in response togenerating the index information, generating a checksum of thecompressed source data associated with the plurality of sub-blocks; anddetermining whether the checksum of the source data in the uncompressedformat matches the checksum of the compressed source data.
 20. Themethod of claim 19, further comprising: in response to determining thatthe checksum of the source data in the uncompressed data format matchesthe checksum of the compressed source data, verifying that the sourcedata was properly compressed.